Internet Info 1997 December/Internet_Info_CD-ROM_Walnut_Creek_December_1997.iso/ietf/urn/urn-archives/urn-ietf.archive.9703/000029_owner-urn-ietf _Wed Mar 12 16:50:05 1997.msg

Internet Message Format | 1997-04-01 | 4KB

Received: (from daemon@localhost)
    by services.bunyip.com (8.8.5/8.8.5) id QAA08369
    for urn-ietf-out; Wed, 12 Mar 1997 16:50:05 -0500 (EST)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1])
    by services.bunyip.com (8.8.5/8.8.5) with SMTP id QAA08364
    for <[e-mail]>; Wed, 12 Mar 1997 16:50:02 -0500 (EST)
Received: from acl.lanl.gov by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b)
        id AA24804  (mail destined for [e-mail]); Wed, 12 Mar 97 16:50:00 -0500
Received: from montana (montana.acl.lanl.gov [128.165.147.143]) by acl.lanl.gov (8.7.3/8.7.3) with SMTP id OAA20510 for <[e-mail]>; Wed, 12 Mar 1997 14:49:59 -0700 (MST)
Message-Id: <[e-mail]>
X-Sender: [e-mail]
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Date: Wed, 12 Mar 1997 14:49:12 -0700
To: [e-mail]
From: "Ron Daniel Jr." <[e-mail]>
Subject: [URN] NAPTR changes
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: [e-mail]
Precedence: bulk
Reply-To: "Ron Daniel Jr." <[e-mail]>
Errors-To: [e-mail]

Hi,

I've modified the NAPTR draft to accomodate the remarks collected during
the WG last call period. Here is a paraphrase of the comments and the
changes I made. The full copy of the -04 version of NAPTR will follow
in a seperate message.

1) Karen Sollins asked that the abstract be modified to mention that NAPTR
   is an experimental resolver disovery service.

That has been done.

2) Karen also suggested that the POSIX ERE syntax be summarized in an
   appendix to assist those who don't have a copy of the POSIX spec handy.

I took another look at the POSIX ERE specification. I do not think that I
can accurately summarize it in a reasonable amount of time, short of
repeating it verbatim. The probability of coming up with something that is
not quite interoperable is too high.

If someone wants to implement a NAPTR-handling system, there are a number of
free and commercial regular expression packages they can use. Or, if they
insist on rolling their own, they can do an inter-library loan of the
spec. Given the availability of this material, I don't believe that failure
to provide such a summary presents a serious impediment to implementation.
Further, I think interoperability is better served by having people rely on
the real specification.

3) Karen also suggested that the security considerations section was
   not detailed enough. In a different message, Ed Lewis suggested that it
   was probably OK.

I have added one paragraph to that section which states that any security
considerations for communicating with a particular resolver are outside
the bounds of this spec but must be addressed in the specifications for
resolver communication protocols.

4) Ed Lewis pointed out some flaws in my BNF for the substitution expression
   grammar, and raised the issue of host names vs. domain names.

I changed the grammar, and added a statement that the output of the
substitution expression MUST result in a string that obeys the syntax
of DNS host names.

5) Martin Duerst raised the question of how the regular expressions should
   deal with %encoded characters - in their encoded or binary form?

I added a statement that the URN Syntax draft defines a canonical form for
URNs, which %encodes characters outside a limited repertoire. The regular
expressions MUST be constructed to operate on the canonical form of a URN.
Since this means we have to match %encoded characters, the regexps are
going to be especially ugly. Sorry.


I'll send the -04 version of the draft to the list in just a minute.

Regards,

Ron Daniel Jr.              voice:[phone]
Advanced Computing Lab        fax:[phone]
MS B287                     email:[e-mail]
Los Alamos National Lab      http://www.acl.lanl.gov/~rdaniel
Los Alamos, NM, USA, 87545